NedFox XML Envelope

Below is an example of the Envelope which can be found in all NedFox XML messages.

 

    <xs:complexType>
      <xs:sequence>
        <xs:element name="Envelope" type="xsi:Envelope" maxOccurs="1" minOccurs="1"/>
        <xs:element name="Messages" type="xsi:Messages" maxOccurs="1" minOccurs="1"/>
      </xs:sequence>
      <xs:attribute name="version" type="xs:string" use="required"/>
    </xs:complexType>
  </xs:element>
  <xs:complexType name="Envelope">
      <xs:sequence>
        <xs:element name="FromPartyNumber" type="xs:long" maxOccurs="1" minOccurs="1"/>
        <xs:element name="FromPartyName" maxOccurs="1" minOccurs="0"/>
        <xs:element name="ToPartyNumber" type="xs:long" maxOccurs="1" minOccurs="1"/>
        <xs:element name="ToPartyName" maxOccurs="1" minOccurs="0"/>
        <xs:element name="InterchangeReference" minOccurs="1" maxOccurs="1"/>
        <xs:element name="InterchangeDateTime" minOccurs="1" maxOccurs="1"/>
        <xs:element name="InterchangeTest" type="xs:boolean" minOccurs="0" maxOccurs="1"/>
      </xs:sequence>
  </xs:complexType>

 

The available fields are described below:

Envelope/FromPartyNumber The partynumber of the sending party. If this message is delivered directly at Retail3000, no routing by RetailLink is required and the partynumber can be set to 9999999999999 (13x9). Off course its allowed to send a 'real' partynumber, the recognition within RetailVista of the source addresses is better readable in that case.
Envelope/FromPartyName For support purpose it's nice to set the readable name of the sending party
Envelope/TopartyNumber

The partynumber of the receiving party. This should be the EDI center (if availlable) of the receiving/addressed party. If not partynumber is available, use the partynumber of the receiving party itself.

If this message is delivered directly at Retail3000, no routing by RetailLink is required and the partynumber can be set to 9999999999999 (13x9). Off course its allowed to send a 'real' partynumber, the recognition within RetailVista of the source addresses is better readable in that case.

Envelope/ToPartyName For support purpose it's nice to set the readable name of the receiving party
Envelope/InterchangeReference An unique ID for the message transfer session. The Interchange ID can be used by for example the supportdesk to follow a message through a number of systems. If the message is delivered directly at Retail3000, the reference can be left empty.
Envelope/InterchangeDateTime The Date and Time the Interchange started
Envelope/InterchangeTest If True this message is a test message and will not be accepted in production environments.